Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts OI: Trap exploder reports trap receiver error 'SNMP-D-EAGENTUSMWINDOW-Agent REPORT [USM]: Not In Time Window.' (359648)

Last Updated: 6/12/2020Categories: TroubleshootingTotal Views: 4720Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Smarts Trap exploder reports the following trap receiver error:

SNMP-D-EAGENTUSMWINDOW-Agent REPORT [USM]: Not In Time Window.

The following error is found in Smarts Trap receiver log:

Cause

SNMP V3 has added security features, one of which is the timestamps in SNMP packets to prevent replay attacks. When the SNMP trap receiver receives the first trap from sm_snmp, it creates an entry in its internal table representing its estimate of the time on the trap sender. The SNMP trap receiver will then compare its estimate with newly received traps (or other SNMP V3 responses) from that agent to verify that the packet is not being replayed.

Using sm_snmp to send the trap means that you execute sm_snmp each time. That means sm_snmp acts as if was just restarted and sets the engine boot time accordingly. To the trap receiver, this looks like an identical packet to the one already received. The trap receiver expects a packet with a timestamp that represents the remote agent having advanced by the time between the first and second traps. So the trap handler reports "Not In Time Window" if you wait longer than the time window (150 seconds) between sending the first and second traps.

If the Smarts Trap receiver log is also reporting *Error!* Mangled value. Then the issue is with the device snmpagent not sending out the proper engine-boot or engine-time values.

OCTET-STRING (0x04), 11 bytes == xxxxxxxxxxxx
67: usm-authentication-parameters ->
OCTET-STRING (0x04), 12 bytes == (hex) d4 4e ee 57 5a 4f 0b ba dd c8 fe 2a
81: usm-privacy-parameters ->
OCTET-STRING (0x04), 8 bytes == *Error!* Mangled value.
00091: Remainder of the bad packet follows.
{ 04, 66, 6a, 8a, eb, c5, 18, b6, d1, 83, a1, 39 ....

Resolution

If the message in the log is limited to SNMP-D-EAGENTUSMWINDOW-Agent REPORT [USM]: Not In Time Window. The Smarts trap receiver is working as designed and will continue to process traps as required.

If the Smarts Trap receiver log is also reporting *Error!* Mangled value. Then the issue is with the device snmpagent not sending out the proper engine-boot or engine-time values.  The vendor needs to be consulted to resolve the issue with the snmp-agent.
It is recommended that the customer run a packet capture on the device for snmp v3 traffic to provide the vendor with the evidence so they can resolve the issue.

Workaround

The work around is to configure the device to send snmp v2 traps and the trap receiver to process the trap from the device as snmp v2.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant